System and/or methods for distributing advertisements from a central advertisement network to a peripheral device via a local advertisement server

ABSTRACT

Certain exemplary embodiments disclosed herein relate to systems and/or methods for distributing advertisements from a central advertisement network to one or more peripheral devices at a location via a local advertisement server. In certain exemplary embodiments, the local advertisement server within a location receives advertisements from the central advertisement network and rebroadcasts them to peripheral devices within that location. Advertising information may be tracked and reported, e.g., for accounting, revenue-sharing, and/or other purposes in certain exemplary embodiments. Thus, in certain exemplary embodiments, the distribution of advertisements is provided to peripherals via a non-web- and non-PC-dependent network. Moreover, in certain exemplary embodiments, reporting and advertising related communications are substantially bi-directional regardless of device type. Certain exemplary embodiments provide revenue sharing among some or all of the central advertising network provider, the proprietors of locations, operators tasked with maintaining the local ad server and/or the peripheral devices, etc.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Application Ser. No. 61/006,382, the entire contents of which are hereby incorporated herein by reference.

TECHNICAL FIELD

The exemplary embodiments disclosed herein relate to systems and/or methods for distributing advertisements to one or more peripheral devices. More particularly, certain exemplary embodiments relate to systems and/or methods for distributing advertisements from a central advertisement network to one or more peripheral devices at a location via a local advertisement server. In certain exemplary embodiments, the local advertisement server within a location receives advertisements from the central advertisement network and rebroadcasts them to peripheral devices within that location. Advertising information may be tracked and reported, e.g., for accounting, revenue-sharing, and/or other purposes in certain exemplary embodiments.

BACKGROUND AND SUMMARY

Various advertising schemes have been developed over the years. For example, an early advertising scheme still used today involves printing advertisements and recording information about the “impressions.” Impression information tends to reflect the subject matter of the advertisement, the general audience targeted, the location where printed, etc. Another common advertising scheme involves inserting commercials into television programming. Again, “impressions” about the advertisement are recorded. An advertising technique that has gained prominence in the Internet age has been banner and pop-up type advertisements. Impressions may be recorded, e.g., in the form of cookies or the like, and sometimes may be reported back to a local server. Based on these and/or other information, including demographic, taste, shopping habit, and/or other comparisons, it has sometimes been possible to attempt to more precisely target advertisements to users.

Unfortunately, such advertising techniques suffer several disadvantages. For example, it often is difficult to accurately record impression information for printed advertisements and television commercials. Although it is possible to get an idea about the broad area and/or audience covered, the time of day a spot was run, and general demographic information about neighborhoods and/or television viewers, it is difficult to capture more detailed and/or more precise impression information. Banner and pop-up ads are able to gather more information about a user and/or a user's computer. However, the information still may be limited based on privacy settings set by the user and/or technical challenges related to the network-based connections. Moreover, such advertisements typically are limited to exposure on a personal computer.

There are also problems associated with the effect of advertisements on users. Oftentimes, printed advertisements are simply discarded. Television commercials increasingly are being ignored or completely skipped (e.g., through the proliferation of digital video recorders and “TV on DVD” style offerings). More recently, banner and pop-up ads tend to be viewed as intrusive and a violation of privacy. Accordingly, numerous attempts have been made to try to filter or reduce the appearance of banner and pop-up ads on computers. Unsolicited email messages have been labeled “spam,” are subject to email client filters, and even have been the subject of several bills sponsored in both houses of the U.S. Congress.

In view of the above, a further problem exists in that although digital advertisement distribution techniques present a better chance of reaching potential customers in new and engaging ways while also allowing advertisers to gather more detailed impression information, they tend to be subject to more criticism and to technology-based filtering.

Therefore, it will be appreciated that there is a need in the art for improved digital advertisement distribution techniques. It also will be appreciated that there is a need in the art for systems and/or methods for distributing advertisements from a central advertisement network to one or more peripheral devices at a location via a local advertisement server.

One aspect of certain exemplary embodiments disclosed herein relates to a local advertisement server located in an out-of-home (OOH) location and connected to a central advertising network being configured to cause advertisements to be displayed on a peripheral device.

Another aspect of certain exemplary embodiments relates to a peripheral device for use in an out-of-home location configured to display ads from a local advertisement server connected to a central advertising network.

Still another aspect of certain exemplary embodiments relates to a method of displaying advertisements on a peripheral device connected to a local server in an out-of-home location.

Yet another aspect of certain exemplary embodiments relates to an advertising system including a local advertisement server, the local advertisement server being located in an out-of-home location and being connected to a central advertising network such that it is configured to cause advertisements to be displayed on a peripheral device.

In certain exemplary embodiments, a local advertisement server is provided. A network connection to a central advertising network located remote from the local advertisement server is provided. A storage location is configured to store an advertisement database, with the advertisement database including advertisements received from the central advertising network via the network connection along with content control data associated with each said advertisement. A local connection to one or more peripheral devices located in the same location as the local advertisement server is provided. A display controller is configured to cause the one or more peripheral devices connected to the local advertisement server via the local connection to display at least some of the advertisements received from the central advertising network in dependence on the content control data associated with the advertisements.

In certain exemplary embodiments, an advertisement system or network comprising a plurality of such local advertisement servers is provided, with each said local advertisement server being located at a different location.

In certain exemplary embodiments, an advertising method for providing a plurality of electronic advertisements to peripheral display devices distributed across a plurality of locations is provided. A plurality of local advertisement servers are provided, with each said local advertisement server being located at a different location. A central advertising network located remote from the local advertisement servers is provided. At least some electronic advertisements are distributed from the central advertising network to the local advertisement servers via network connections provided to the respective local advertisement servers. Advertisement databases are stored via storage locations provided to the respective local advertisement servers, with the advertisement databases including electronic advertisements received from the central advertising network via the respective network connection along with content control data associated with each said electronic advertisement. At each said local advertisement server, at least one advertisement queue is maintained. Each said local server further comprises a display controller configured to cause any peripheral display devices connected thereto to display at least some of the electronic advertisements received from the central advertising network in dependence on the content control data associated with the electronic advertisements and the respective at least one advertisement queue. Each said electronic advertisement is one of a leader board, banner, or media clip. The content control data for each electronic advertisement comprises indications of how and when the associated electronic advertisement should be displayed.

These aspects and exemplary embodiments may be used separately and/or applied in various combinations to achieve yet further embodiments of this invention. Additionally, the exemplary embodiments described herein may be implemented as any suitable combination of programmed logic circuitry (e.g., as any suitable combination of hardware, software, firmware, and/or the like). In certain exemplary embodiments, computer readable storage mediums also may be provided.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features, aspects, and advantages of the instant invention will be further understood by review of the following detailed description of the exemplary embodiments when read in conjunction with the appended drawings, in which:

FIG. 1 is an illustrative simplified system view of a central advertisement network in connection with a plurality of local ad servers respectively located at a plurality of locations, in accordance with an exemplary embodiment;

FIG. 2 is an illustrative simplified view of a location including a local ad server and a plurality of devices to which ads from the ad server will be distributed, in accordance with an exemplary embodiment;

FIG. 3 is a simplified block diagram showing components comprising a local ad server, in accordance with an exemplary embodiment;

FIG. 4 is a simplified block diagram showing components comprising a device to which ads from the ad server will be distributed, in accordance with an exemplary embodiment;

FIG. 5 is an illustrative display showing how advertising content may be included with main content, in accordance with an exemplary embodiment;

FIG. 6 shows illustrative transmission data associated with a new device being connected to a local ad server or an already connected device being updated, in accordance with an exemplary embodiment;

FIG. 7 shows illustrative transmission data associated with a new ad being sent from the central advertisement network to a local server, in accordance with an exemplary embodiment;

FIG. 8 shows illustrative reporting data that may be sent from a local server to the central advertisement network, in accordance with an exemplary embodiment;

FIG. 9 is a flowchart showing an illustrative process for setting up a new location in accordance with an exemplary embodiment;

FIG. 10 is a flowchart showing an illustrative process for updating information about a location in accordance with an exemplary embodiment;

FIG. 11 is a flowchart showing an illustrative process for distributing advertisements to a location from a central advertisement network in accordance with an exemplary embodiment;

FIG. 12 is a flowchart showing an illustrative process for distributing advertisements from a local ad server at a location to peripheral devices in that location in accordance with an exemplary embodiment; and

FIG. 13 is a flowchart showing an illustrative process for reporting data to the central advertisement network in accordance with an exemplary embodiment.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Certain exemplary embodiments disclosed herein relate to systems and/or methods for distributing advertisements from a central advertisement network to one or more peripheral devices at a location via a local advertisement server. In certain exemplary embodiments, a local advertisement server within a location receives advertisements from the central advertisement network and rebroadcasts them to peripheral devices within that location. Advertising information may be tracked and reported, e.g., for accounting, revenue-sharing, and/or other purposes in certain exemplary embodiments. Thus, in certain exemplary embodiments, the distribution of advertisements is provided to peripherals via a non-web- and non-PC-dependent network. Moreover, in certain exemplary embodiments, reporting and advertising related communications are substantially bi-directional regardless of device type. This, it is possible in certain exemplary embodiments to record “impressions” of digital advertisements, including information such as, for example, when the advertisement was “printed,” where the advertisement was “printed,” who saw the advertisement, etc. It is also possible in certain exemplary embodiments to provide revenue sharing among some or all of the central advertising network provider, the proprietors of locations, operators tasked with maintaining the local ad server and/or the peripheral devices, etc.

1. Exemplary System Components

This section provides an overview of exemplary system components that may be used in connection with certain exemplary embodiments. For example, this section provides an overview of the overall advertisement distribution system, local ad servers, and peripheral devices. Of course, it will be appreciated that the following descriptions are provided by way of example and without limitation. Thus, for example, other techniques apart from those described herein may be used in connection with the exemplary embodiments described herein, as may various combinations and sub-combinations of the exemplary techniques described herein.

1.1 Exemplary System Overview

Referring now more particularly to the drawings, FIG. 1 is an illustrative simplified system view of a central advertisement network in connection with a plurality of local ad servers respectively located at a plurality of locations, in accordance with an exemplary embodiment. The central advertisement network 100 is connected to the local ad servers 104 a-c, which are respectively located at locations 102 a-c, via a plurality of respective connections 101 a-c. The connections 101 a-c may be, for example, Internet connections, WAN connections, etc. The central advertisement network 100 includes a database (not shown) of advertisements that are distributable to the local ad servers 104 a-c at the locations 102 a-c. The advertisements stored in the database of advertisements may be categorized in various ways. For example, the advertisements may be categorized by product and/or service type; the type of advertisement (e.g., a leader board, banner, media clip, audio clip, video clip, etc.); the devices on which the ad should be displayed (e.g., only on televisions, only on jukeboxes, only for registered users, on handheld gaming machines and countertop boxes but not televisions, etc.), and/or in other ways.

The central advertisement network 100 also is configured to receive reporting information from the local ad servers 104 a-c providing, for example, information related to the respective locations 102 a-c, the advertisements shown, etc. Based on this information features such as revenue sharing, advertisement targeting, etc., may be provided. Further details of the reporting between the local ad servers 104 a-c and the central advertisement network 100 will be provided in further detail below.

1.2 Exemplary Local Advertisement Server

Within each location 102, a local ad server is configured to communicate with a plurality of local devices 106 operably connected thereto. Thus, in general, a local ad server 104 is configured to receive advertisements from the central advertisement network 100 and is further configured to cause such advertisements to be displayed on one or more local devices 106 operably connected thereto. FIG. 2 is an illustrative simplified view of a location including a local ad server and a plurality of devices to which ads from the ad server will be distributed, in accordance with an exemplary embodiment. As noted above, there is a connection 101 from the central advertisement network 100 to the local ad server 104 in the location 102. Within the location 102, the local ad server 104 may be connected to the local devices on which the advertisements are to be displayed in any appropriate manner. As shown in FIG. 2, the local devices (also sometimes called peripheral devices) include televisions 202 a-b, a jukebox 204, countertop devices 206 a-b (e.g., bar-top game devices, jukebox terminals, and/or the like), handheld gaming devices 208 a-b, and user peripheral devices 210 a-b (e.g., laptops, mobile phones, PDAs, and/or the like). Of course, other peripheral devices may be operably connected to the local ad server 104. In certain example implementations, the local ad server 104 is connected to the televisions 202 a-b via a wired connection 203, which may be, for example, a composite audio/video, component audio/video, coax, HDMI, S-video, F-pin, and/or any other suitable type connection. In certain example implementations, the local ad server 104 is connected to the jukebox 204 and the countertop devices 206 a-b via a network connection 205 (e.g., an Ethernet network connection). In certain example implementations, the local ad server 104 may include a wireless transceiver 105, e.g., to communicate with wireless transceivers 209 a-b of the handheld gaming devices 208 a-b, respectively, and the wireless transceivers 211 a-b of the user peripheral devices 210 a-b, respectively. As will be described in greater detail below, the communications between the local ad server 104 and the peripheral devices within the location 102 may occur over a predefined protocol and/or may include one- or two-way transmission of data depending on the use case involved. It will be appreciated that other peripheral devices may be included in a location together with or in place of some or all of those shown in FIG. 2.

FIG. 3 is a simplified block diagram showing components comprising a local ad server, in accordance with an exemplary embodiment. A data bus 302 and a processor 304 facilitate the processing of data including, for example, the receiving of new advertisements from the central advertising network 100 via an advertising network connection 306, the causing of such advertisements to be displayed on the peripheral devices via a local network connection 308, etc. As noted earlier, the local network connection 308 may be an Ethernet connection or any other suitable connection (e.g., a LAN, WAN, wireless, infrared, dial-up, or other connection). Similarly, the advertising network connection 306 may be an Ethernet connection or any other suitable connection (e.g., a LAN, WAN, wireless, infrared, dial-up, or other connection). These connections therefore may facilitate the sending of information from the local ad server 104 to the central advertisement network 100 including, for example, information about the location, peripheral devices at the location, users frequenting and/or using the peripheral devices at the location, etc. Similarly, these connections may facilitate the sending of information from the local ad server 104 to the peripheral devices including, for example, the advertisements and associated data, log files, etc.

Advertisements sent from the central advertising network 100 and received by the local ad server 104 via the central ad network connection 306 may be stored in an advertisement database 310 or other suitable storage location of or associated with the local ad server 104 (e.g., on a disk drive device, flash media, USB device, in a memory location, etc.). Advertisements in the advertisement database 310 of the local ad server 104 may be in the form of, for example, leader boards, banners, audio/video media clips, audio clips, video clips, etc., and thus may be stored in any suitable format (e.g., as image files, moving GIFs, MPEG-2 or other format video files, Flash media, MP3 audio, etc.). In addition to the data file(s) corresponding to the advertisements, additional information associated with the advertisements also may be stored. For example, a unique identifier of the advertisement may be stored, as may the type or format of advertisement, and/or other content control data (e.g., when the ad should be played, how often it should be played, appropriate audience information, priority information, associations with particular songs, games, or web or television programming, etc.).

The local ad server 104 also may maintain a listing of connected devices, for example, in a device database 312 or other suitable storage location. Such a device database 312 may include all of the peripheral devices located in the particular location to which advertisements are to be distributed. It will be appreciated that certain types of peripheral devices may not be able to display certain types of advertisements. For example, a jukebox may be able to display audio and/or video advertisements, whereas a handheld gaming device may only be able to support banners and/or leader boards. Thus, along with such a listing of connected devices, information such as the types of advertisements displayable on the list may be displayed. Similarly, a peripheral devices may not include a dedicated storage location of its own for storing ads to be displayed, for maintaining queues of ads to be displayed, for maintaining log files, etc. For example, a television may not include its own storage location, whereas a user peripheral device may include its own storage location. Accordingly, such information may be stored in the device database 312 (e.g., as flags indicative of the corresponding features). Certain exemplary embodiments may, in turn, read and interpret such flags and accordingly maintain queues, log files, etc., on behalf of the particular devices incapable of maintaining their own queues, log files, etc.

As alluded to above, one or more log files 314 may be stored on the local ad server 104. A first type of log file may log information about communications between the central advertisement network 100 and the local ad server 104 related to the distribution of advertisements. For example, such a log file may log successful transmissions of advertisements from the central advertisement network 100 to the local ad server 104 along with a time/date stamp of the beginning and/or end of the transfer, and/or other information pertaining to such transfers. A second type of log file may log information about communications between the peripheral devices and the local ad server 104 related to advertisement-based reporting. Such log files may identify the advertisements played, the time of the playing, the device on which it was played, any events associated with the play (e.g., whether a song was playing, a television station was being shown, etc.), information about the particular customer using the device (e.g., when the user has registered, demographic information about the registered user may be logged, etc.), and/or the like. A third type of log file may log transmissions of the second type of log file (e.g., information related to advertisement-based reporting) between the local ad server 104 and the central advertisement network 100. Some or all of these log files 314 may be updated via the local ad server 104 or via the peripheral devices connected thereto.

It will be appreciated that the advertisement database 310, the device database 312, and/or the log files 314 may be encrypted. Such encryption may reduce the chances of a user tampering with the distribution of advertisements, reporting erroneous advertisement plays, etc. This may be advantageous in certain exemplary embodiments, for example, when revenue is shared based on advertising activities of the location, for accounting to advertisers, for ensuring that proper paid-for advertisements are not replaced with other unpaid-for advertisements, etc.

The local ad server 104 also may be connected to a media source 315. The media source 315 may be, for example, a television antenna, a cable or satellite connection, a DVD or other media player, etc. In such a case, the local ad server 104 may be configured to include advertisement material directly into the media stream from the media source 315. That is, the ad server 104 may add layers of advertisements (e.g., banners, leader boards, other advertisements) to the original media stream, may insert media content (e.g., video clips, pictures, slide shows, etc.) in the place of normal commercials included in the broadcast, may shrink or otherwise transform the media stream so as to add advertising content around the edges of the media stream, etc. An illustrative arrangement for the layering and/or insertion is described below, e.g., with reference to FIG. 5. A media-out port 316 may then distribute the modified content to the appropriate peripheral(s), e.g., via an Ethernet connection, a connection suitable for a television, etc.

Although not shown in FIG. 3, one or more queues of advertisements for display on the peripherals may be maintained by the local ad server 104. For example, one master queue may be maintained in certain exemplary embodiments such that advertisements are synchronized throughout all connected peripherals, e.g., causing all peripherals to display a common advertisement, a common advertisement type, common advertisement subject matter, different advertisements, advertisements are displayed in a round-robin format, etc. Multiple queues also may be maintained in certain exemplary embodiments, e.g., such that one queue is maintained for each peripheral device, one queue is maintained for each peripheral device type, etc. The peripherals may consult this queue or these queues when displaying advertisements, or the local ad server 104 itself may instruct the peripheral devices to display advertisements in accordance with the queue or queues.

Although the local ad server 104 has been described as relating to a separate component, it will be appreciated that a local ad server comprising programmed logic circuitry may be integrated into or included in another component, possibly even a peripheral device. Thus, in certain exemplary embodiments, a local ad server may be integrated into or included in, for example, a jukebox, a countertop device, etc. Indeed, the peripheral device itself may be used solely for advertisements, and/or for advertisements and/or another more conventional function (e.g., the peripheral devices may be used for purposes other than advertising in some cases). In such cases, the local ad server may be implemented as described herein, e.g., as any suitable combination of programmed logic circuitry including, for example, any suitable combination of hardware, software, firmware, and/or the like. The components may be shared with or separate from the underlying peripheral device. For example, a common storage location may be used, separate logical partitions of a common storage location may be used, or separate storage locations may be provided. Similarly, the same or different network connections may be provided (e.g., a single network connection in a jukebox, for example, may serve as a connection to an audiovisual distribution network and/or to the central advertisement network). Similarly, in certain exemplary embodiments, the same or different processors may be used. Furthermore, in certain exemplary embodiments where a local server is built into a digital jukebox device, the digital jukebox device may be configured to retrieve instances of media for playback via a central audiovisual network, with the central audiovisual network being the same network as the central advertising network.

1.3 Exemplary Peripheral Devices

A wide variety of peripheral devices may be used in connection with the ad servers of certain exemplary embodiments. For example, a peripheral device according to certain exemplary embodiments may include programmed logic circuitry (e.g., any suitable combination of hardware, software, firmware, and/or the like) for receiving advertisements from a local ad server and for displaying such advertisements. In such exemplary embodiments, the advertisement may be transmitted to the device and stored in a storage location or database and played back later, and/or streamed for substantially direct playback. The corresponding functionality may be included in the peripheral device directly (e.g., through the addition of a new software module or based on the original equipment manufacturer design). Such exemplary embodiments advantageously may be used in connection with, for example, countertop devices, jukeboxes, handheld gaming devices, etc.

In another example, a peripheral device according to certain exemplary embodiments may include programmed logic circuitry for interrupting the normal flow of content to insert advertisements from a local ad server. In such cases, an additional component may be provided to the display peripheral to interrupt the normal flow of media. For example, programmed logic circuitry may be interposed between a video display card and an actual display, e.g., to capture the video display signals generated by the video display card and to modify the signals so as to include the content accordingly before sending the modified signals to the actual display. Thus, it may be possible in certain exemplary embodiments to add layers, insert content, reformat displays, etc., in order to include custom advertising content from a local ad server. Such exemplary embodiments advantageously may be used in connection with, for example, countertop devices, jukeboxes, handheld gaming devices, televisions, etc.

In still other examples, e.g., in the case of a television or other unintelligent display, programmed logic circuitry may be provided to the peripheral to stream in and play back already modified content which may be, for example, content with custom advertisements inserted as commercials, as layers over the broadcast, etc. Thus, the normal flow of content will already be modified before reaching the peripheral device for playback.

In yet other examples, users using devices may be prompted to register themselves. Based on this information, ads may be displayed directly to the peripheral device. Thus, registered users may essentially “invite” advertisements, e.g., when viewing web pages, logging onto to the Internet from a particular location, playing a game at a location on a user's own device, etc. Moreover, by registering or at least by being identified (e.g., as a user on a jukebox, a player of a game on a countertop device, etc.), additional content in the form of advertisements may add to the expected user experience. The additional content may be, for example, customized advertisements (e.g., ads that incorporate personal information such as name and/or age, ads specifically targeted for an individual selected based on a model for example, ads for products or services a person is or seems to be interested in, etc.). The additional content also may be extra advertising content that ordinarily would not be expected. For example, pop-up advertisements, banners, movie clips, and/or the like may be displayed at a time when the user does not expect them to appear (e.g., when a user is selecting a song on a jukebox, in between levels of a game, in small windows of a handheld device, etc.). It is also possible to provide other types of additional advertising content to users, regardless of whether they are registered and/or identified.

Thus, it is possible to provide the advertising techniques of certain exemplary embodiments on both interactive and non-interactive peripherals. Moreover, as explained in greater detail below, interactive devices may enable further custom delivery of advertisements, e.g., to registered and/or tracked users.

FIG. 4 is a simplified block diagram showing components comprising a device to which ads from the ad server will be distributed, in accordance with an exemplary embodiment. A data bus 402 and a processor 404 facilitate the processing of data including, for example, the receiving of new advertisements from the local ad server 104 via an local network connection 406, the causing of such advertisements to be displayed on displays of the peripheral device 106, etc. As above, the local network connection 406 may be an Ethernet connection or any other suitable connection (e.g., a LAN, WAN, wireless, infrared, dial-up, or other connection).

The peripheral device with ad server support 106 may include a local advertisement database 410. The local advertisement database 410 may store advertisements to be displayed on the peripheral device 106 received from the local server 104. Information about when the ad should be displayed, the frequency for display, events that trigger the ad, etc., may be stored in the local advertisement database 410. An advertisement queue 414 may be included in the local advertisement database 410 or it may be a separate component.

The advertisement queue 414 may facilitate the ordering of advertisements for playback. It may be based on information associated with the advertisements stored in the local advertisement database 410, ultimately traceable back to the central advertisement network 100. The ordering may be based on, for example, the amount an advertiser has paid for the advertisement to be displayed, events triggering a particular advertisement (e.g., every time a particular song is played on a jukebox, an associated advertisement might be displayed), absolute times of days in which ads should be played (e.g., an advertisement may be setup for playback at a particular time every day or on certain days, etc.), and/or based on other factors. The advertisement queue 414 also may be organized as a playlist of advertisements. Such a playlist of advertisements may be integrated into or associated a playlist of instances of media, e.g., on a jukebox in certain exemplary embodiments. Advertisements also may be scheduled using the same or similar techniques, with such scheduling being accomplished by an advertiser, a proprietor of a location, etc.

One or more logs 412 may be kept and/or stored on the local peripheral device 106. A first type of log corresponds to data pertaining to updates from the local ad server. For example, the success or failure of a particular advertisement update may be stored, as may the particular advertisements updated, the date/time of the update, etc. A second type of log pertains to the actual playback of advertisements. For example, an identifier of the advertisement may be logged, along with the date/time of the playback, the number of playbacks, an event associated with the playback, etc.

A local ad server may be updatable remotely and/or in person. In the former case, remote downloads may be scheduled as described in greater detail below. In the latter case, updating may be done by a traveling operator, using, for example, a storage device such as a USB device, flash media, CD or DVD, etc. Similarly, the transmission of log files also be take place remotely and/or by a traveling operator. In general, then, transmissions (e.g., log file transmissions, advertisement updates, etc.) may be performed substantially in real-time, in batch at a scheduled or forced or other time (e.g., when a dial-up connection is used), in person, etc.

The local peripheral device 106 also may include display programmed logic circuitry 408. In certain exemplary embodiments, the display programmed logic circuitry 408 simply may integrate the advertisement to be played back into the normal content. For example, a webpage or video stream may be modified, a game screen may be reformatted, etc. In certain exemplary embodiments, the display programmed logic circuitry 408 may temporarily interrupt the normal flow of a stream to playback the advertisement, e.g., by replacing standard commercial content, by pausing a game or instance of media queued for playback on a device, etc. In still other exemplary embodiments, the display programmed logic circuitry 408 may be integrated into the peripheral device 106 such that the playback of advertisements is substantially seamless and integrated into the main content in a manner transparent to the user.

As alluded to above, peripheral devices may be used to provide interactions with advertisements. Thus, an advertisement may be changed based on user interaction with the peripheral device. In one exemplary implementation, a display on a suitably configured device may display an advertisement. The display may invite or prompt the user of the device or those capable of viewing the display to take an action, e.g., send a text message (e.g., an SMS message), email an address, select an area of the display, etc. The input may be processed by the local ad server directly or indirectly (e.g., input may be processed by the peripheral device and log files about the interaction may later be shared with the local ad server and/or the central advertising network) to bring about a particular result. The inputs to the advertisement may cause, for example, responders to be entered into a drawing or giveaway (e.g., a “text to win” scenario), free credits for plays on a jukebox to be dispensed (e.g., credited to a user account or directly to a user via a rewards card or other payment device, etc.), songs to be moved up in queue based on voting, various similar or different commercial products or services to be ranked (e.g., colas, beers, vacuums, etc.), discounts to be applied to products (e.g., that finish first in a voting contest), coupons to be dispensed, etc. In other words, the advertisements may be displayed in response to input provided, directly or indirectly, by a person to whom the electronic advertisements is targeted. The displayed advertisements themselves may be changed in dependence on the input. For example, advertisements for more highly ranked products may be displayed more often, popular advertisements may be displayed more frequently, etc.

FIG. 5 is an illustrative display showing how advertising content may be included with main content, in accordance with an exemplary embodiment. Certain exemplary embodiments create a new display 500 that includes the main content 502 as well as advertising content. In the example shown in FIG. 5, first and second advertising content 504 and 506 are included in the new display 500. The first and second advertising content 504 and 506 may be added as layers over top of the main content 502 in certain exemplary embodiments, whereas the first and second advertising content 504 and 506 may be added around shrunken down main content 502 in certain other exemplary embodiments. It will be appreciated that the main content 502 may be reduced in one dimension so as to permit the addition of content in that dimension whereas other content may be overlaid onto existing content in another dimension. It also will be appreciated that although two advertising content sections are shown, the present invention is not limited to only two advertising content sections or the respective formats thereof. For example, in certain exemplary embodiments, a single advertising area may be substantially square-shaped and may be displayed opaquely or semi-transparently over some or all of the main content 502.

In certain exemplary embodiments, if a connection to the central advertisement network is temporarily lost or damaged, the local ad server may at least temporarily store information for later transmission. Similarly, if a connection between the peripherals and the local ad server is temporarily lost or damaged, the peripherals may at least temporarily store information for later transmission. This may occur before, during, and/or after real-time and/or scheduled transmissions of log files, and the central advertisement network, local ad server, and/or peripheral devices may anticipate such outages and/or respond to them in one or more of the techniques set forth herein and/or in other ways, e.g., to ensure that data is transmitted as appropriate. In a case where storage is not provided to a peripheral device, a peripheral device operably connected thereto may at least temporarily serve as a local ad server, serving advertisements and/or storing data. This may take place until the connection is repaired or reestablished. In this and/or other ways, certain exemplary embodiments provide a local ad server that it operable over a non-web-dependent and/or non-PC dependent network. Moreover, communications are substantially bi-directional regardless of device type, insofar as data may be logged and advertisements distributed in dependence on a central coordinating local ad server. Similarly, in certain example implementations, if the local ad server is damaged, one or more of the peripheral devices may be configured to communicate directly with the central advertisement network.

2. Exemplary Data Transmissions

This section provides examples of the types of information that may be included in communications between, for example, the central advertisement network 100 and the local ad server 104, and between a local ad server 104 and a peripheral device. More particularly, FIG. 6 shows illustrative transmission data associated with a new device being connected to a local ad server or an already connected device being updated, in accordance with an exemplary embodiment; FIG. 7 shows illustrative transmission data associated with a new ad being sent from the central advertisement network to a local server, in accordance with an exemplary embodiment; and FIG. 8 shows illustrative reporting data that may be sent from a local server to the central advertisement network, in accordance with an exemplary embodiment.

2.1 Illustrative New/Updated Device Transmission Data

Referring more particularly to FIG. 6, new device/device update transmission data 600 may be sent from a peripheral to a local ad server 104, and/or from a local ad server 104 once it has been received to the central advertisement network 100. A new peripheral connected in a suitably configured location may automatically (e.g., without direct user prompting) transmit such information in certain exemplary embodiments. In certain exemplary embodiments, a user may input such information into a local ad server 104, e.g., using a user interface provided thereto. The new device/device update transmission data 600 includes a device id 602, which uniquely identified the device that has been added to the location or has been updated (e.g., been upgraded to be able to process further advertisement types, communicate over a wireless connection instead of a wired connection, etc.). The device type 604 also is specified. The device type 604 may be indicative of a television, a jukebox, a countertop device (e.g., a bar-top game device, a jukebox terminal, and/or the like), a handheld gaming device, a user peripheral device (e.g., a laptop, a mobile phone, a PDA, and/or the like), etc. The ad types supported 606 also may be specified. In certain exemplary embodiments, this information may be at least partially populated automatically (e.g., as mobile phones are capable of supporting SMS messages, televisions are capable of supporting video playback, jukeboxes are capable of supporting audio content, etc.).

A flag for indicating whether the peripheral includes its own storage location 608 may be set to indicate whether advertisements may or should be sent to the peripherals, e.g., in advance of when they should be played back. If the flag 608 indicates that the peripheral includes its own storage location, content may be distributed, in whole or in part, to the peripheral some time before it is to be displayed. If the flag 608 indicates that the peripheral does not include its own storage location, the local ad server 104 may only distribute advertisements to the peripheral device when it is to be displayed (e.g., when a commercial is to be replaced, when a new banner is to be displayed on a webpage, etc.).

A flag for indicating whether the peripheral maintains its own queue 610 may be set to indicate whether the peripheral itself will or should maintain its own queue of advertisements. If the flag 610 indicates that the peripheral will maintain its own queue, the queue may be configured by the local ad server 104 once or periodically and left to the peripheral for actual real-time management. If the flag 610 indicates that the peripheral will not or should not maintain its own queue, a queue may be set up on the local ad server 104 itself, or the peripheral device may be tagged so that it controlled in accordance with a master queue maintained by the local ad server 104.

A flag for indicating whether the peripheral maintains its own logs 612 may be set to indicate whether the peripheral itself will or should maintain its own log files. If the flag 612 indicates that the peripheral will maintain its own logs, the peripheral will or should maintain its own logs and the local ad server 104 will periodically or aperiodically retrieve such logs. If the flag 612 indicates that the peripheral will not or should not maintain its own logs, the local ad server 104 will maintain log files on behalf of the peripheral device. This may require further communications between the peripheral device and the local ad server 104, or it may not if a queue is also maintained by the local ad server 104 rather than the peripheral device.

2.2 Illustrative New Advertisement Transmission Data

Referring more particularly to FIG. 7, a new advertisement data 700 may be sent from the central advertisement server 100 to a local ad server 104, and/or from a local ad server 104 to a peripheral device. The new advertisement data 700 may include the advertisement content 702 itself. The advertisement content 702 may be in any appropriate form, such as, for example, an image file, a moving GIF, an MPEG-2 or other format video file, Flash media, MP3 audio, etc. A unique advertisement id 704 may be included to help track plays and/or distribution of the associated advertisement. The advertisement type 706 (e.g., leader board, banner, media clip, audio clip, video clip, etc.) also may be stored. This information may help the local ad server 104 determine which advertisements may be displayed on the peripheral devices, for example, by enabling a comparison between the information from the new/updated device transmission data 600 and the ad type 706 included in the new advertisement transmission data 700. This may be accomplished by having the local ad server 104 filter and distribute advertisements based at least on advertisement type as appropriate, or by having the peripheral devices initiate requests for all suitable advertisement types.

The new advertisement transmission data 700 also may include content control data 708. Such content control data 708 may include information such as, for example, when the advertisement should be played (e.g., time of day, day of week, special events, special occasions, holidays, etc.), the frequency at which the advertisement should be played (e.g., no more than X times per hour or per day, etc.), the audience for which the advertisement is appropriate (e.g., sports or music enthusiasts, persons over the age of 18 or 21, certain targeted demographic populations, etc.), priority information (e.g., the advertisement may be ranked according to a numerical or other value and then inserted into a queue or scheduled for playback in dependence on the priority information, etc.), whether the advertisement is associated with a particular event or occasion (e.g., every time a touchdown is scored, at the top of every hour, whenever a bartender initiates a signal, etc.), and/or other similar information.

2.3 Illustrative Reporting Data

Referring more particularly to FIG. 8, reporting data 800 may be sent from a peripheral to a local ad server 104, and/or from a local ad server 104 to the central advertisement network 100. In certain exemplary embodiments, at least some of the reporting data 800 may be supplied by a peripheral device (e.g., data corresponding to the particular advertisements displayed), while some of the information may be provided by the local ad server 104 (e.g., data corresponding to the location, that may be irrelevant or unknown to the peripherals). In certain exemplary embodiments, the data form the peripheral devices may be included within or wrapped by data from the local ad server 104.

The reporting data 800 may include a location id 802 that uniquely identifies the location of the local ad server 104 and the peripheral devices. The location id 802 may be user specified or assigned, e.g., by the central advertisement network 100. Location demographic data 804 also may be included in the reporting data 800. The location demographic data 804 may include information about customers (e.g., average age or age range, racial makeup, typical composition, etc.), the type of venue (e.g., a bar, club, lounge, restaurant, hotel, etc.), the music played or television watched (which may be detailed or summary information from a jukebox or television), revenue information (e.g., how much the location has grossed or netted in a particular night, how much money is generated from or dedicated to advertising, etc.), and/or other information. The location demographic data 804 may be provided to the central advertisement network 100 only once, with every reporting transmission, periodically (e.g., once a week, month, year, etc.), when requested by the central advertisement network 100, when initiated by a user at the location (e.g., to signal a significant change in one or more categories), etc.

The reporting data 800 also may include detailed advertising data 806. The advertising data 806 may be grouped, e.g., by advertisement id, advertisement type, advertisement subject matter, etc.; it may be ordered, e.g., by date/time, by advertisement id, by advertisement subject matter, etc.; or it might not be so categorized or ordered. The advertising data 806 thus may include the advertisement id, as well as information as to when the advertisement was played (e.g., date/time, day of week, etc.), the device on which the advertisement was played, any content that was played when the advertisement was played (e.g., a song or television program, etc.), information about the customer (e.g., when the customer is registered), etc.

3. Illustrative Use Cases

This section provides information related to several common use cases that may arise during the operation of a local ad server. It will be appreciated that the following is provided by way of example and without limitation. For example, other use cases may arise, and/or the use cases specified below may be handled in similar and/or other ways.

3.1 Setting Up a New Location

FIG. 9 is a flowchart showing an illustrative process for setting up a new location in accordance with an exemplary embodiment. In step S902, the local ad server is setup. In step S904, information related to the location, clientele of the location, etc., is provided, e.g., to a user interface provided to the local ad server. In step S906, the local ad server is configured to communicate with the central advertisement network. This may involve configuring firewalls, setting up proxy servers, specifying a common day/time for updates, etc. Any peripheral devices are setup in step S908. This may include installing programmed logic circuitry for use with the peripheral devices (e.g., to configure devices to communicate with the local ad server by, for example, installing a software module, providing a hardware module to interrupt the flow of content, etc.). The peripheral devices are then configured to communicate with the local ad server in step S910. This may involve configuring wireless connections, providing information about the peripheral devices to the local ad server, etc. In step S912, the peripheral device information is provided to the central advertisement network. The information provided in this use case may be updated as necessary, e.g., in accordance with the following use case.

3.2 Updating Information about a Location

FIG. 10 is a flowchart showing an illustrative process for updating information about a location in accordance with an exemplary embodiment. In step S1002, the user logs into local ad server. In step S1004, the user identifies whether the location information or the peripheral device information is to be updated. In step S1006, the user provides updated information about the location or existing device, or adds a new peripheral. It will be appreciated that a new peripheral may need to be setup at or before this point. This updated information is saved in step S1008, and it is communicated to the central advertisement network in step S1010. Thus, the system is dynamic in that more or fewer devices may be added and/or changed once a location is initially configured.

3.3 Distributing Advertisements to a Location

FIG. 11 is a flowchart showing an illustrative process for distributing advertisements to a location from a central advertisement network in accordance with an exemplary embodiment. In step S1102, the user causes the local ad server to log into the central advertisement network. In step S1104, the central advertisement network verifies that the local ad server is a genuine local ad server. This may be accomplished by checking the location id, by checking a username and/or password combination, etc. Any updates about the location are provided to the central advertisement network in step S1106. Any advertisement updates are downloaded in step S1108. This step may further comprising filtering a catalog of available advertisements based on, for example, the location demographics, device types at the location, advertisement types supported by the peripheral devices at the location, retrieving not previously downloaded or previously improperly retrieved (partial or corrupted) advertisements, etc. Log files are updated in step S1110, and the local ad server logs off of the central advertisement network in step S1112.

3.4 Distributing Advertisements to Peripheral Devices within a Location

FIG. 12 is a flowchart showing an illustrative process for distributing advertisements from a local ad server at a location to peripheral devices in that location in accordance with an exemplary embodiment. In FIG. 12, it is determined whether an update to the peripheral devices is needed in step S1202. This may be initiated by the local ad server (e.g., as a push of new information), by the peripheral devices (e.g., as a pull of new information), in a according to a publish-and-subscribe behavior, at a particular predefined update time, based on a user trigger, etc. Updates may include advertisement updates, updates to the programmed logic circuitry (e.g., software updates, firmware upgrades, etc.), and/or the like. If there are updates, in step S1204, they are distributed to the peripherals based on, for example, device type, advertisement types supported, whether a user using a user peripheral device is a registered user, etc. Log files are updated in step S1206.

Additionally, a proprietor of a location may decide to filter advertisements per area of a location and/or type of device. For example, certain advertisements may be appropriate for a bar area of a hotel's restaurant, but inappropriate for the hotel's lobby. Similarly, devices of a particular kind may be configured to receive different ads than other devices. For example, more generally appealing and/or non-offensive advertisements may be displayed on large television displays viewable by a large number of persons, but handheld devices of a particular brand and/or that attract a certain demographic may be configured to receive a full panoply of different advertisements.

With respect to the registration of users, certain exemplary embodiments may maintain a database of registered users. Users may provide certain information (e.g., name, contact info, demographic info, etc.) to the location. In exchange, the user may be rewarded with credits, free plays, coupons, free drinks, promotional material, entry into a sweepstakes, etc. Advertisements may be further targeted to the registered user, e.g., based on the information provided by the user, when the user logs into a device (e.g., a jukebox, a handheld gaming device, the user's own laptop, etc.). Moreover, the profile of the registered user may be updated over time, for example, as the registered user initiates more plays on a jukebox, plays more games on a countertop device, etc.

3.5 Reporting Advertising Information to the Central Advertisement Network

FIG. 13 is a flowchart showing an illustrative process for reporting data to the central advertisement network in accordance with an exemplary embodiment. In FIG. 13, it is determined whether a report to the central advertisement network is needed in step S1302. This may be initiated by the local ad server (e.g., as a push of new information), by the central advertisement network (e.g., as a pull of new information), in a according to a publish-and-subscribe behavior, at a particular predefined update time, based on a user trigger, etc. If a report is needed, in step S1304, data is gathered from the peripherals. The data gathered may include advertisement data (e.g., as described in connection with FIG. 8). The data from the peripherals may be organized into any predefined format, and additional information may be added by the local ad server (e.g., with updates about the location, etc.), in step S1306. The organized data may be transmitted to the central advertisement network in step S1308.

4. Exemplary Revenue Sharing Techniques

It is possible to implement revenue sharing in connection with certain exemplary embodiments. Advertisers pay for their advertisements to be distributed through the central advertisement network to a wide variety of locations. Revenue may be shared between one or more of the central advertisement network provider, the proprietor of the location, and any operators tasked with the maintenance of the local ad servers and/or the peripheral devices. The sharing of revenue may be based on predefined percentages (e.g., the central advertisement network provider earns a first percentage, the proprietor of the location earns a second percentage, and an operator earns a third percentage) or based on a formula or revenue sharing model. Such a revenue sharing model may take into account the number of advertisements shown (e.g., the more advertisements, the higher the percentage), the number of peripheral devices on which advertisements are shown (e.g., the more peripherals, the higher the percentage), the number of locations and/or peripherals managed by an operator (e.g., the more locations and/or peripherals, the higher the percentage), and/or the like.

The calculation of revenues may be facilitated by the logging of information and the transmission of such information to the central advertisement network. In particular, data may be logged to an accounting database in connection with the central advertisement network, and revenue sharing programmed logic circuitry in connection with the accounting database may interpret the stored data and calculate how much revenue should be shared among whom. This revenue sharing programmed logic circuitry may run at predefined intervals, on the occasion of predefined events, and/or when initiated by a user. For example, the revenue sharing programmed logic circuitry may calculate revenue shares once a day, once a month, every time the central advertisement network communicates with one or more local ad servers, when new advertisements are distributed, etc. Once it is determined how revenue should shared, the revenue may be disbursed (e.g., by direct deposit to a bank, by crediting an account, by sending a check, etc). The disbursement of revenues may be performed at a frequency the same as or different from the frequency at which the revenue sharing programmed logic circuitry is executed. Thus, the revenue sharing scheme may, for example, allow the central advertisement network provider, proprietors of locations, operators, and/or advertisers to share backend profits earned directly or indirectly based on an advertisement at a location.

A protocol may be implemented to track and provide rewards for such advertisements in certain exemplary embodiments. One known protocol already has been developed by Zoom Media, and it may be used in connection with certain exemplary embodiments.

Advertising on peripherals also may reduce the costs associated with purchasing and/or maintaining the peripherals, e.g., when such peripherals are allowed to operate in a “sponsored mode,” or other mode where advertisements may be played along with the main content offering. In certain exemplary embodiments, it may be possible to turn on and off advertisements and to adjust the pricing or subsidizing of such peripherals in dependence on the amount of time the advertisements are on, the number of advertisements shown, the types of advertisements shown, etc.

Certain exemplary embodiments may provide a mechanism for advertisers to very precisely control the placements of their ads and/or where and how to make their “impressions.” For example, proprietors of a location may provide very detailed information about their locations, including, for example, physical location (e.g., down to the intersection and/or address of a location), type of establishment (e.g., bar, restaurant, club, arcade, etc.), them of the establishment (e.g., hip-hop club, line dancing bar, Tex-Mex restaurant, etc.), type of music traditionally played (e.g., rock music, hipster scene, jazz club, etc.), and/or other information. Advertisers may define an advertising campaign, e.g., by defining rules as to where and/or how to advertise, may select locations individually or in groups, etc. For example, an advertising campaign may be setup within a geographic region, with a particular theme or type, combinations of the above and/or other features identified by a location, etc. To these and/or other ends, an advertiser interface may be configured to allow advertisers to define or redefine an advertising campaign by creating at least one rule specifying how and where an advertisement should be run. The advertiser interface may be accessible via the central advertising network.

The amount charged to the advertiser may be based on the campaign defined. The complexity of the campaign may help determine price (e.g., more complex campaigns cost more). Also, the number and/or type of the impressions also may help determine price. For example, based on actual historical and/or projected data about one or more selected locations, advertisements may be priced accordingly. The central advertisement network may predict a certain number of total impressions, which may sometimes be further broken down by type of advertisement, peripheral on which the advertisement was displayed, etc. The user may then be charged according to a fixed or sliding scale in dependence on the number of ads shown and/or predicted to be shown.

It will be appreciated that certain exemplary embodiments described herein may be implemented as programmed logic circuitry (e.g., any suitable combination of hardware, software, firmware, and/or the like). Also, the exemplary embodiments described herein, and/or components thereof, may be stored on a computer readable storage medium, e.g., as instructions. It will be appreciated that the aspects and exemplary embodiments may be used separately and/or applied in various combinations to achieve yet further embodiments of this invention.

While the preferred aspects of the invention have been illustrated and described herein, it will be apparent to one of ordinary skill in the art that various changes and/or modifications can be made. Thus, the specific description herein is meant to be exemplary only and is not intended to limit the invention beyond the terms of appended claims. 

1. A local advertisement server, comprising: a network connection to a central advertising network located remote from the local advertisement server; a storage location configured to store an advertisement database, the advertisement database including advertisements received from the central advertising network via the network connection along with content control data associated with each said advertisement; an advertisement server advertisement queue; a local connection to a plurality of peripheral devices and a digital jukebox device located in the same location as the local advertisement server, the jukebox device and at least some of said peripheral devices including respective storage locations and being configured to maintain respective jukebox device and peripheral device advertisement queues and log files, and to cause advertisements to be displayed from the respective advertisement queues without directly consulting the advertisement server advertisement queue; and a display controller configured to cause peripheral devices connected to the local advertisement server via the local connection that do not include their own peripheral device advertisement queues to display at least some of the advertisements received from the central advertising network using the advertisement server advertisement queue and in dependence on the content control data associated with the advertisements.
 2. The local advertisement server of claim 1, wherein each said advertisement is one of a leader board, banner, or media clip.
 3. The local advertisement server of claim 2, wherein the content control data for each advertisement comprises indications of how and when the associated advertisement should be displayed.
 4. The local advertisement server of claim 1, further comprising a plurality of log files, a first log file comprising information regarding the distribution of advertisements from the central advertising network to the local advertisement server, and a second log file comprising information regarding the display of advertisements on the peripheral devices.
 5. The local advertisement server of claim 1, further comprising a media source connection configured to receive media from an external media source, wherein the display controller is further configured to combine, in a predetermined format, the advertisements with the media received from the external media source via the media source connection to create a combined signal, the combined signal being sent to at least some of the peripheral devices for possible subsequent display.
 6. The local advertisement server of claim 1, wherein the advertisement server advertisement queue includes an advertisement queue for each peripheral device type, the display controller being further configured to cause peripheral devices connected to the local advertisement server via the local connection to display at least some of the advertisements received from the central advertising network in dependence on the content control data associated with the advertisements and the associated advertisement queue.
 7. The local advertisement server of claim 3, wherein the local advertisement server is built into the digital jukebox device.
 8. The local advertisement server of claim 7, wherein the local advertisement server and the digital jukebox device share a common processor and/or storage location.
 9. The local advertisement server of claim 8, wherein the digital jukebox device is configured to retrieve instances of media for playback via a central audiovisual network, the central audiovisual network being the same network as the central advertising network.
 10. The local advertisement server of claim 1, wherein the display controller is further configured to change or modify the advertisements being displayed in response to input provided, directly or indirectly, by a person to whom the advertisement is targeted.
 11. The local advertisement server of claim 1, further comprising an advertiser interface configured to allow advertisers to define or redefine an advertising campaign by creating at least one rule specifying how and where an advertisement should be run, said advertiser interface being accessible via the central advertising network.
 12. An advertisement system comprising a plurality of the local advertisement servers of claim 1, each said local advertisement server being located at a different location.
 13. An advertising method for providing a plurality of electronic advertisements to peripheral devices distributed across a plurality of locations, the method comprising: providing a plurality of local advertisement servers, each said local advertisement server being located at a different location; providing a central advertising network located remote from the local advertisement servers; distributing at least some electronic advertisements from the central advertising network to the local advertisement servers via network connections provided to the respective local advertisement servers; storing, via storage locations provided to the respective local advertisement servers, advertisement databases, the advertisement databases including electronic advertisements received from the central advertising network via the respective network connection along with content control data associated with each said electronic advertisement; causing, at each said local advertisement server, at least one advertisement server advertisement queue to be maintained; wherein each said local server is connected to a plurality of peripheral devices and a digital jukebox device, the jukebox device and at least some of said peripheral devices including respective storage locations and being configured to maintain respective jukebox device and peripheral device advertisement queues and log files, and to cause advertisements to be displayed from the respective advertisement queues without directly consulting the advertisement server advertisement queue, wherein each said local server further comprises a display controller configured to cause peripheral display devices connected thereto that do not include their own peripheral device advertisement queues to display at least some of the electronic advertisements received from the central advertising network in dependence on the content control data associated with the electronic advertisements and the respective at least one advertisement server advertisement queue, wherein each said electronic advertisement is one of a leader board, banner, and media clip, and wherein the content control data for each electronic advertisement comprises indications of how and when the associated electronic advertisement should be displayed.
 14. The method of claim 13, further comprising causing, at each said local advertisement server: media to be received from an external media source; a combining, in a predetermined format, via the respective display controllers, of the electronic advertisements with the media received from the external media source to create a combined signal; the combined signal to be sent to peripheral display devices connected to the local advertisement server for display on the respective peripheral display device.
 15. The method of claim 13, wherein each said local advertisement server is built into the digital jukebox device to which the advertisement server is connected.
 16. The method of claim 15, wherein each said local advertisement server shares a common processor and/or storage location with the associated digital jukebox device.
 17. The method of claim 16, wherein each said the digital jukebox device is configured to retrieve instances of media for playback via a central audiovisual network, the central audiovisual network being the same network as the central advertising network.
 18. The method of claim 13, further comprising causing, at each said location, a changing or modifying to the electronic advertisements being displayed in response to input provided, directly or indirectly, by a person to whom the electronic advertisements is targeted.
 19. The method of claim 13, further comprising receiving input, via an advertiser interface, configured to allow advertisers to define or redefine an advertising campaign by creating at least one rule specifying how and where an electronic advertisement should be run, said advertiser interface being accessible via the central advertising network.
 20. The method of claim 13, further comprising receiving input when a new peripheral device is connected to a local advertisement server, the input including an identifier for the new peripheral device, as well as indications as to what ad types the new peripheral device supports, whether the new peripheral device has a dedicated storage location associated therewith, and whether the new peripheral device maintains its own advertisement queue and/or log files. 